Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of relax import for_each validation into v1.10 #36136

Conversation

github-actions[bot]
Copy link
Contributor

Backport

This PR is auto-generated from #36119 to be assessed for backporting due to the inclusion of the label 1.10-backport.

The below text is copied from the body of the original PR.


Import blocks with for_each were intended to require resource blocks with a matching expansion. This validation however did not take place in prior releases, and configurations with this mismatch currently exist in production.

That simple validation also does not take into account a single resource instance inside of an expanded module, which is a valid use case and harder to check for at the point of validation. That will still fail correctly during plan if the targets are not available.

We can skip this validation for now, and work on generating static validation errors later on if possible, taking into account the expanded module case.

Fixes #36111


Overview of commits

@github-actions github-actions bot force-pushed the backport/jbardin/import-expansion-validation/hardly-glowing-titmouse branch from afdba45 to 14394d7 Compare November 29, 2024 15:34
@github-actions github-actions bot requested a review from jbardin November 29, 2024 15:34
@jbardin jbardin marked this pull request as ready for review November 29, 2024 15:36
@jbardin jbardin merged commit 571db67 into v1.10 Nov 29, 2024
6 checks passed
@jbardin jbardin deleted the backport/jbardin/import-expansion-validation/hardly-glowing-titmouse branch November 29, 2024 15:48
Copy link
Contributor Author

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Copy link
Contributor Author

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant